-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated to collect dpkg.log and verify installed files. Also, search for package name that contains installed files. #253
Conversation
Updated to collect dpkg.log and verify installed files. Also, search for package name that contains installed files.
aecea77
to
d1d2e1d
Compare
Do you know if we can do the same for additional package managers such as pacman, brew, zipper...? |
I've tried
I believe zypper can check file paths as well as dpkg/rpm.
|
I have found a useful table. pacman/Rosetta - ArchWiki |
As for |
Add /usr/lib, /usr/lib32, /usr/lib64, /usr/libx32
I did some tests on some debian (dpkg), redhat (rpm) and arch (pacman) based systems and the collection time was increased by approximately 10 to 15 min in some situations. Also, it seems that From Ubuntu 22.04:
During my tests I did not notice lots of false positives for From AIX 7.3:
As the Thanks a lot! |
Thanks for testing this. |
Added collection of which installed package owns a specific file or command. Note that this artifact is resource-intensive and time-consuming to execute, so it is disabled by default in all profiles
@mnrkbys can you review the changes, please? |
Thanks @tclahr |
Added an artifact to collect /var/log/dpkg.log to artifacts/files/packages/dpkg.yaml.
Added an artifact to verify files installed from dpkg package. This is similar to the "rpm -q -a" command in artifacts/live_response/packages/dpkg.yaml.
And I also added artifacts that search for packages that contain installed files. Files not included in a package may have been installed manually, helping to find suspect files.
As you know, /bin is a symbolic link to /usr/bin. Therefore, whether the installation destination directory is /bin or /usr/bin, the files are installed in the same directory.
However, "dpkg -S /bin/ls" and "dpkg -S /usr/bin/ls" return different results. Therefore, "dpkg -S" must be executed for both file paths.
"dpkg -S /bin/ls" vs "dpkg -S /usr/bin/ls"
But, "rpm -q -f" will returns same results.
"rpm -q -f /bin/ls" vs "rpm -q -f /usr/bin/ls"